fix(test): file.spec.131 moveTo may fail due to read order assumption #643
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Platforms affected
tests
Motivation and Context
On iOS (and I think any file api I've ever used), reading directories does not define any particular order of files. The iOS implementation uses contentsOfDirectoryAtPath:error: which states:
While this test does not appear to be failing actively on GH actions, it was failing for me locally due to the expectation assuming that they will be in a particular order.
Description
Reworked the test so that it will scan for each expected value and keep track which ones it has found.
Assertions of the expected item count remains.
Asserts that each item is found.
Testing
Ran mobilespec locally on iOS.
Checklist
(platform)
if this change only applies to one platform (e.g.(android)
)